Provider Bulk Sync
Use Cases
Provider Bulk Sync
Context
Life Sciences or Health Cloud organizations’ teams (Sales, MSLS and KAMs) engage with Healthcare providers and organizations to provide information about their products and how they can help improve treatment outcomes. The primary goal of these teams is to expand reach and provide education while ensuring that HCPs' and HCOs' time is used efficiently by talking about the right products and messages based on their interests and specializations.
To achieve this, it is important to have correct and verified data about HCPs and HCOs. This connector (API) enables organizations to bring such data from industry-leading OneKey Data into Life Sciences or Health Cloud.
Scenario
Cumulus Pharma, a company that makes medicines, has released a new diabetes management drug. They want to tell healthcare professionals about how good and effective the drug is.
To reach these HCPs, Cumulus needs accurate HCP data from trusted sources, consolidated into a single source of truth and made available in the CRM system their commercial teams work in.
Today, getting this data into the CRM is only semi-automated and time-consuming, because data from third-party sources or Master Data Management (MDM) organizations must first be transformed to fit the CRM data model.
Solution
Organizations with an IQVIA OneKey agreement can use this connector to directly import HCP and HCO data into the Life Sciences for Customer Engagement or Health Cloud.
Using an organization's OneKey credentials, the connector not only retrieves data but also automatically transforms it to fit the LSC for Customer Engagement or Health Data Model. This streamlined process significantly reduces the time it takes to get to market.
Benefits
- Reduce Time to Market with quick access to industry-recognized data.
- Data is available in Life Sciences for Customer Engagement or Health Cloud, so teams are more productive than when they work across multiple systems.
What's Supported Out of the Box
The connector ships to support one core use case: a bulk and delta sync of IQVIA OneKey HCP and HCO data into Life Sciences or Health Cloud. Out of the box, it:
- Sources data from IQVIA OneKey only (an active OneKey agreement is required).
- Runs an initial full load, and then delta syncs that continue from the last delivery so that only new or updated records are pulled. If no starting delivery is supplied, the next OneKey delivery is used.
- Targets a single OneKey territory per sync request, so each territory is synced with its own request.
- Syncs HCP (Individual) and HCO (Workplace) accounts, along with their related data such as NPIs, specialties, addresses, phones, and business licenses, plus best contact times for HCOs and education and languages for HCPs.
- Maps every HCP to a single Account record type, and every HCO to a single Account record type.
- Classifies affiliations by type: Activity records (HCP to HCO) are always Hard, Individual relations (between HCPs) are always Soft, and Workplace relations (between HCOs) are Hard when the link is a configured hierarchy type and Soft otherwise.
- Applies one generic field mapping to all records, while you configure which countries' reference data (codes and picklist values) is downloaded.
Anything beyond this, such as HCP or HCO subtypes, per-country affiliation rules or field translations, segmentation, or a dedicated application per region, is a supported extension rather than default behavior. See the Setup and Extend Connector guides for details.